Turbine engine fleet wash management system

ABSTRACT

A turbine engine fleet wash management system is configured to electronically communicate with a turbine engine system, a fleet management service, and a cleaning management service. The turbine engine fleet wash system causes a cleaning of a turbine engine to occur based on information received from the turbine engine system and other sources. The turbine engine fleet wash management system includes a cleaning schedule optimizer that generates a cleaning schedule based on engine health monitoring data, engine operation data, maintenance schedules for the turbine engine, and cleaning regimen data. The cleaning schedule optimizer estimates turbine engine performance improvements based on the selected cleaning regimen, and calculating an estimate of carbon credits earned based on the predicted improvement in turbine engine performance.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/749,241, filed 24 Jun. 2015, which claims priority to and the benefitof U.S. Provisional Patent Application No. 62/087,000, filed 3 Dec.2014, the disclosures of which are both now expressly incorporatedherein by reference.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to gas turbine engines and morespecifically to systems that manage the cleaning of gas turbine engines.

BACKGROUND

Gas turbine engines are used to power aircraft, watercraft, generators,and the like. Gas turbine engines typically include an engine corehaving a compressor, a combustor, and a turbine. The compressorcompresses air drawn into the engine and delivers high pressure air tothe combustor. In the combustor, fuel is mixed with the high pressureair and is ignited. Products of the combustion reaction in the combustorare directed into the turbine where energy is extracted to drive thecompressor and the fan. Leftover products of the combustion areexhausted out the engine core to provide additional thrust.

Dirt and grime is accumulated in gas turbine engines from atmosphericair ingested and fuel burned during operation. As dirt and grime buildup in turbofan engines, the performance of those engines may be reduceddue to aerodynamic and frictional losses. To reduce the dirt and grimein the turbofan of a gas turbine engine, a cleaning agent (usuallywater) may be sprayed into the engine core.

SUMMARY

The present application discloses one or more of the features recited inthe appended claims and/or the following features which, alone or in anycombination, may comprise patentable subject matter.

In an example 1, a system to optimize cleaning of a turbine engineincludes one or more computing devices configured to: by a communicationlink between a turbine engine and a cleaning schedule optimizer, receiveengine health data from the turbine engine over time during operation ofthe turbine engine; by the cleaning schedule optimizer, periodicallyexecute an cleaning optimization routine to evaluate instances of theengine health data using one or more cleaning schedule optimizationcriteria; and in response to one or more instances of the engine healthdata meeting an engine health criterion, cause a foamed cleaning agentto be discharged into the turbine engine according to an optimizedengine cleaning schedule.

An example 2 includes the subject matter of example 1, wherein thecleaning schedule optimizer only executes the cleaning optimizationroutine if the system determines that engine performance is degrading.An example 3 includes the subject matter of example 1 or example 2,wherein the cleaning schedule optimizer is configured to query anoperational database to obtain information about the use of the turbineengine and incorporate the turbine engine use information into theoptimization routine. An example 4 includes the subject matter of any ofexamples 1-3, wherein the cleaning schedule optimizer is configured toquery an environmental database for information about operatingenvironments of the turbine engine and incorporate the operatingenvironment information into the optimization routine. An example 5includes the subject matter of any of examples 1-4, wherein the cleaningschedule optimizer is configured to query a maintenance database forinformation about the maintenance history of the turbine engine andincorporate the maintenance history information into the optimizationroutine. An example 6 includes the subject matter of any of examples1-5, wherein the cleaning schedule optimizer is configured to query acleaning parameters database for information about the differentcleaning regimens available for use on the turbine engine andincorporate the cleaning regimen information into the optimizationroutine. An example 7 includes the subject matter of any of examples1-6, and includes a fuel efficiency calculator electrically connected toan engine health monitor, wherein the fuel efficiency calculator isconfigured to receive one or more engine performance parameters andgenerate fuel efficiency parameters based upon the received engineperformance parameters. An example 8 includes the subject matter ofexample 7, wherein the fuel efficiency calculator is configured tocalculate the changes in fuel consumption in the engine over time. Anexample 9 includes the subject matter of example 8, wherein the fuelefficiency calculator is configured to calculate the changes inoperating cost over time based on the changes in fuel consumption overtime. An example 10 includes the subject matter of example 7, andincludes a carbon credit calculator configured to receive the fuelefficiency parameters and the engine performance parameters, estimate achange in fuel consumption based upon the optimized cleaning schedule,and use the estimated change in fuel consumption to calculate anestimated number of carbon credits earned. An example 11 includes thesubject matter of example 10, and includes a notification system incommunication with the cleaning schedule optimizer and coupled to anetwork, wherein the notification system is configured to send anotification to an owner of the turbine engine, and wherein thenotification comprises the cleaning schedule, the estimated fuelconsumption, and the estimated carbon credits.

In an example 12, an engine cleaning optimizer embodied in one or moremachine accessible storage media includes instructions executable by acomputing system comprising one or more computing devices to cause thecomputing system to: periodically receive instances of engine healthmonitoring data produced by a turbine engine during operation of theturbine engine; with the instances of engine health monitoring data,calculate an engine health parameter; with the engine health parameter:compute an indicator of engine performance degradation; compute anindicator of fuel consumption; and with the fuel consumption indicator,estimate a carbon credit that would result from cleaning the turbineengine; with the engine performance indicator, the fuel consumptionindicator, and the estimated carbon credit, generate an optimizedcleaning schedule; and initiate discharge of a foamed cleaning agentinto the turbine engine in accordance with the optimized engine cleaningschedule.

An example 13 includes the subject matter of example 12, and includesinstructions executable to generate the cleaning schedule for theturbine engine system by algorithmically evaluating the indicator ofengine performance degradation. An example 14 includes the subjectmatter of example 13, and includes instructions executable to generatethe cleaning schedule for the turbine engine system by algorithmicallyevaluating a cost of cleaning. An example 15 includes the subject matterof example 14, and includes instructions executable to generate thecleaning schedule for the turbine engine system by algorithmicallyevaluating an estimated fuel savings. An example 16 includes the subjectmatter of example 15, and includes instructions executable to generatethe cleaning schedule for the turbine engine system by algorithmicallyevaluating an amount of time until the next schedule maintenance for theengine. An example 17 includes the subject matter of example 16, andincludes instructions executable to generate the cleaning schedule forthe turbine engine system by algorithmically evaluating a likelyeffectiveness of the cleaning. An example 18 includes the subject matterof example 17, and includes instructions executable to generate thecleaning schedule for the turbine engine system by algorithmicallyevaluating an estimate of carbon credits earned. An example 19 includesthe subject matter of any of examples 12-18, and includes instructionsexecutable to modify the optimized cleaning schedule in response to dataindicative of a maintenance schedule for the turbine engine. An example20 includes the subject matter of any of examples 12-19, and includesinstructions executable to communicate with a computing system of theengine manufacturer to schedule maintenance intervals based on dataindicative of parts or modules that need replacement. An example 21includes the subject matter of any of examples 12-20, and includesinstructions executable to issue a prompt to prevent the occurrence of ascheduled cleaning cycle in response to a determination that a regularlyscheduled maintenance is to occur. An example 22 includes the subjectmatter of any of examples 12-21, and includes instructions executable tocoordinate the optimized cleaning schedule with a maintenance scheduleand an operational schedule of the turbine engine. An example 23includes the subject matter of any of examples 12-22, and includesinstructions executable to, with the optimized cleaning schedule,specify a time interval between cleanings, the duration of a cleaning,and a composition of cleaning solution used in a cleaning of the turbineengine.

These and other features of the present disclosure will become moreapparent from the following description of the illustrative embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

This disclosure is illustrated by way of example and not by way oflimitation in the accompanying figures. The figures may, alone or incombination, illustrate one or more embodiments of the disclosure.Elements illustrated in the figures are not necessarily drawn to scale.Reference labels may be repeated among the figures to indicatecorresponding or analogous elements.

FIG. 1 is a simplified perspective view of at least one embodiment of aturbine engine cleaning schedule optimizer in electronic communicationwith an aircraft and a cleaning system for cleaning gas turbine engines;

FIG. 2 is a simplified block diagram of at least one embodiment of acomputing system for managing turbine engine cleaning as disclosedherein;

FIG. 3 is a simplified block diagram of at least one embodiment of theturbine engine system of FIG. 2;

FIG. 4 is a simplified schematic diagram showing an environment of thesystem of FIG. 2, including interactions between the components of thesystem of FIG. 2; and

FIG. 5 is a simplified flow diagram of at least one embodiment of amethod for optimizing engine cleaning, which may be performed by one ormore components of the system of FIG. 2, as disclosed herein.

DETAILED DESCRIPTION OF THE DRAWINGS

While the concepts of the present disclosure are susceptible to variousmodifications and alternative forms, specific embodiments thereof areshown by way of example in the drawings and are described in detailbelow. It should be understood that there is no intent to limit theconcepts of the present disclosure to the particular forms disclosed. Onthe contrary, the intent is to cover all modifications, equivalents, andalternatives consistent with the present disclosure and the appendedclaims.

Referring now to FIG. 1, an illustrative cleaning system 10 adapted forcleaning gas turbine engines 12 used in an aircraft 14 is shown. Thecleaning system 10 includes a mobile supply unit 18 and a wand 20coupled to the supply unit 18. The wand 20 is configured to producefoamed cleaner and to discharge the foamed cleaner into the gas turbineengines 12 so that the foamed cleaner can remove dirt and grime built upin the turbine engines 12. The wand 20 of the illustrative embodimentsprays foamed cleaner into the gas turbine engines 12 while the rotatingcomponents of the engines 12 are dry motored so that the foamed cleaneris pulled through the engines 12 as suggested in FIG. 1.

The mobile supply unit 18 included in the cleaning system 10illustratively includes a water supply 32 and a foaming cleaner supply34 mounted to a transport vehicle 36 as shown in FIG. 1. The watersupply 32 illustratively stores and provides de-ionized water to thewand 20. The foaming cleaner supply 34 stores and provides a foamingcleaner to the wand 20. For illustrative purposes, the mobile supplyunit 18 is shown in the back of a truck; however, in other embodiments,the mobile supply unit 18 may be incorporated into a work cart, trailer,or other type of vehicle or support structure. Illustrative embodimentsof the cleaning system 10, including embodiments of the wand 20, aredescribed in U.S. Provisional Patent Application Ser. No. 62/021,939filed Jul. 8, 2014 and entitled “Cleaning System for Turbofan GasTurbine Engines,” U.S. Provisional Patent Application Ser. No.62/032,751 filed Aug. 4, 2014 and entitled “Aircraft Engine CleaningSystem,” and U.S. Provisional Patent Application Ser. No. 62/048,625filed Sep. 10, 2014 and entitled “Wand for Gas Turbine Engine Cleaning.”

A turbine engine cleaning schedule optimizer 232 is in bi-directionalelectronic communication with components of the gas turbine engines 12and the cleaning system 10 by communication links 40 and 42 (e.g., wiredand/or wireless, direct or indirect, connections, as needed). Asdescribed in more detail below, the illustrative turbine engine cleaningschedule optimizer 232 can automatically determine or predict when acleaning of a turbine engine should occur and indicate that the cleaningshould occur, and, in some embodiments, initiates such a cleaning, inaccordance with a schedule that is optimized based on information aboutthe turbine engine 12. The turbine engine information includes, but isnot limited to, data indicative of the current and past performance ofthe turbine engine 12, the environmental conditions in which the turbineengine 12 has operated, the maintenance schedule of the turbine engine12, estimated carbon-credits earned by operation of the aircraft drivenby the turbine engine 12, and/or the predicted efficacy of a selected orrecommended cleaning regimen. For example, some embodiments of thecleaning schedule optimizer 232 can predict a cleaning schedule that isoptimal given a specified optimization objective (e.g., prolong enginelife, improve performance, or improve efficiency), based on historicalengine data and/or other known information.

Referring now to FIG. 2, an embodiment of a fleet wash management system200 for managing turbine engine cleaning for a fleet of aircraft isshown. The illustrative fleet management system 200 includes an enginemonitoring computing device 210, a fleet operations computing device240, one or more networks 260, one or more aircraft systems 270 (e.g.,aircraft 14), and one or more cleaning operations computing devices 280.Each of the components of the fleet management system 200 includescomputer hardware, software, firmware, or a combination thereof,configured to perform the features and functions described herein.

The illustrative engine monitoring computing device 210 includes anengine performance monitor 230 and the cleaning schedule optimizer 232.The cleaning schedule optimizer 232 can create one or more cleaningschedules for a gas turbine engine 12. The cleaning schedule optimizer232 executes one or more mathematical optimization routines to“optimize” the cleaning schedule for the turbine engine 12 (or for theaircraft driven by the turbine engine 12), according to one or moredesired or selected optimization criteria. The cleaning scheduleoptimization criteria includes, for example: maximization of engineperformance, minimization of the turbine engine's carbon footprint,and/or minimization of cleaning or maintenance costs to theowner/operator of the turbine engine.

In more detail, the engine monitoring computing device 210 includeshardware, firmware, and/or software components that are capable ofperforming the functions disclosed herein, including the functions ofthe engine performance monitor 230 and the cleaning schedule optimizer232. The illustrative engine monitoring computing device 210 includes atleast one processor 212 (e.g. a controller, microprocessor,microcontroller, digital signal processor, etc.), memory 214, and aninput/output (I/O) subsystem 216. Portions of the engine monitoringcomputing device 210 may be embodied as any type of computing devicesuch as a desktop computer, laptop computer, or mobile device (e.g., atablet computer, smart phone, body-mounted device or wearable device,etc.), a server, an enterprise computer system, a network of computers,a combination of computers and other electronic devices, or otherelectronic devices. Although not specifically shown, it should beunderstood that the I/O subsystem 216 typically includes, among otherthings, an I/O controller, a memory controller, and one or more I/Oports. The processor 212 and the I/O subsystem 216 are communicativelycoupled to the memory 214. The memory 214 may be embodied as any type ofsuitable computer memory device (e.g., volatile memory such as variousforms of random access memory).

The I/O subsystem 216 is communicatively coupled to a number ofhardware, firmware, and/or software components, including a data storagedevice 218, a display 224, a user interface subsystem 226, acommunication subsystem 228, the engine performance monitor 230 and thecleaning schedule optimizer 232. The data storage device 218 may includeone or more hard drives or other suitable persistent data storagedevices (e.g., flash memory, memory cards, memory sticks, and/orothers). Engine health data 220 and a machine learning database 222reside at least temporarily in the data storage device 218 and/or otherdata storage devices of the fleet management system 200 (e.g., datastorage devices that are “in the cloud” or otherwise connected to theengine monitoring computing device 210 by a network 260). Portions ofthe engine performance monitor 230 and the cleaning schedule optimizer232 may reside at least temporarily in the data storage device 218and/or other data storage devices that are part of the fleet managementsystem 200. Portions of the engine health data 220, the machine learningdatabase 222, the engine performance monitor 230 and the cleaningschedule optimizer 232 may be copied to the memory 214 during operationof the engine monitoring computing device 210, for faster processing orfor other reasons. The display 224 may be embodied as any suitable typeof digital display device, such as a liquid crystal display (LCD), andmay include a touchscreen. The user interface subsystem 226 includes oneor more user input devices (e.g., the display 224, a microphone, atouchscreen, keyboard, virtual keypad, etc.) and one or more outputdevices (e.g., audio speakers, LEDs, additional displays, etc.).

The communication subsystem 228 may communicatively couple the enginemonitoring computing device 210 to other computing devices and/orsystems by, for example, one or more networks 260. The network(s) 260may be embodied as, for example, a cellular network, a local areanetwork, a wide area network (e.g., Wi-Fi), a personal cloud, a virtualpersonal network (e.g., VPN), an enterprise cloud, a public cloud, anEthernet network, and/or a public network such as the Internet. Thecommunication subsystem 228 may, alternatively or in addition, enableshorter-range wireless communications between the engine monitoringcomputing device 210 and other computing devices, using, for example,BLUETOOTH and/or Near Field Communication (NFC) technology. Accordingly,the communication subsystem 228 may include one or more optical, wiredand/or wireless network interface subsystems, cards, adapters, or otherdevices, as may be needed pursuant to the specifications and/or designof the particular engine monitoring computing device 210.

The illustrative communication subsystem 228 communicates output of oneor more of the engine performance monitor 230 and the cleaning scheduleoptimizer 232 to the fleet operations computing device 240 and/or thecleaning operations computing device 280, via a network 260. Forexample, portions of engine health data 220 and/or optimized cleaningschedule data 426, described below, may be supplied to the fleetoperations computing device 240 and/or the cleaning operations computingdevice 280.

Computing devices 240 and 280 utilize the output of the cleaningschedule optimizer 232, such as scheduling notifications, to schedule acleaning of gas turbine engines. As such, computing devices 240 and 280communicate through communication subsystem 256 and communicationsubsystem 296 to ensure that a cleaning occurs at a convenient time forboth the vehicle whose engine is being cleaned and the party providingthe cleaning.

The engine performance monitor 230 is embodied as one or more hardwarecomponents, software components or computer-executable components anddata structures for monitoring and processing data received from aturbine engine system 272. The engine performance monitor 230 monitorsthe health of the turbine engine system 272 by receiving engine healthdata 410, and other related inputs, from an aircraft 270 (from, e.g., aturbine engine system 272 of the aircraft 270). The engine performancemonitor 230 stores portions of the engine health data 410 in the enginehealth database 220, and thereby tracks the engine health data 410 overtime. Based on its analysis of the engine health data 410, the engineperformance monitor 230 generates an assessment of engine performanceand/or engine efficiency. The engine performance monitor 230 providesengine performance information (e.g., a data value indicative of anengine performance assessment, such as an engine performance rating orscore) to the cleaning schedule optimizer 232.

The cleaning schedule optimizer 232 utilizes the engine performanceinformation generated by the engine performance monitor 230 to predictwhen a cleaning will be necessary or desired in order to maintain orimprove the performance of the turbine engine system 272. As usedherein, a “schedule” may refer to a single discrete cleaning event or toa series of cleaning events that are planned according to fixed orvariable time intervals. For example, if an engine 12′s performance isseverely degraded, the cleaning schedule optimizer 232 may initiate asingle cleaning event; whereas, if an engine 12 is currently operatingnormally, the cleaning schedule optimizer 232 may generate a cleaningschedule for the engine 12 at optimized time intervals based on a numberof cleaning schedule criteria including the engine 12's flight plans,normal operating conditions (e.g., short or long duration missions,altitude, humidity, frequency of accelerations vs. cruising segments,etc.), characteristics of the cleaning technique or cleaning solutionused, and/or other factors.

The cleaning schedule optimizer 232 is embodied as one or more hardwarecomponents, software components or computer-executable components anddata structures including a fuel efficiency calculator 234, a carboncredit calculator 236, and an optimization routine 238. The illustrativecleaning schedule optimizer 232 interfaces with the engine performancemonitor 230 to create a cleaning schedule for a turbine engine 12, inorder to maximize performance of the turbine engine 12 and minimizesmaintenance costs. For example, the fuel efficiency calculator subsystem234 and the carbon credit calculator subsystem 236 obtain engineperformance data 412 from the engine performance monitor 230 to estimatethe improved fuel efficiency and estimate the carbon credits earnedresulting from a cleaning of the turbine engine system 272. Theoptimization routine 238 weighs all of the inputs received by thecleaning schedule optimizer 232 and determines whether a cleaning isnecessary.

The turbine engine 12 is a component of a turbine engine system 272 ofan aircraft 270. An illustrative example of a turbine engine system 272is shown in FIG. 3 and described below. As shown in FIG. 3, theillustrative turbine engine system 272 includes an engine controller344, configured with an on-board engine health monitor 346 andcommunication circuitry 348. The engine controller 344 may be embodiedas any suitable computing device or electrical circuitry capable ofperforming the functions described herein (e.g., as a microprocessor,controller, etc.). The communication circuitry 348 enables the enginecontroller 344 to communicate engine health data 410 collected in realtime during operation of the turbine engine system 272 to othercomputing devices, such as the engine monitoring computing device 210,via a network 260 and/or a direct communication link (such as a cable,e.g., when the aircraft 270 is on the ground). While the fleetmanagement system 200 shows a single aircraft 270 for simplicity, itshould be understood that in practice, a number of different aircraft270 may be connected with the fleet management system 200 in a similarfashion.

The illustrative fleet operations computing device 240 is a computingdevice configured to perform aircraft fleet management operations and istypically operated by the owner/operator of the aircraft 270. The fleetoperations computing device 240 can receive data from, e.g., theassociated turbine engine system 272 of an aircraft 270 in a fleet ofaircraft, via, e.g., one or more network(s) 260. The fleet operationscomputing device 240 includes an engine usage database 250 and an enginemaintenance history database 252. The engine usage database 250 storesinformation related to the operation of the turbine engine system 272,such as the number of trips made by the aircraft 270, the duration ofthose trips, the climate conditions in which the trips were made, thedeparture locations and arrival locations of those trips, the date andtime of each trips, the weather conditions during each trips, and otheraircraft operating data. The engine maintenance history database 252stores information related to the maintaining of a turbine engine system272 over time, such as, for example, when the next scheduled enginecheck-up or overhaul is to occur, the entire maintenance history of theturbine engine system 272, and other data related to the past or futuremaintenance of the turbine engine. The fleet operations computing device240 may be embodied as any suitable computing device and/or electricalcircuitry for performing the functions described herein. Accordingly,the remaining components of the fleet operations computing device 240having the same name as above-described components of the enginemonitoring computing device 210 may be embodied similarly; therefore,the description is not repeated here.

The illustrative cleaning operations computing device 280 is a computingdevice configured to manage engine cleaning services, and is typicallyoperated by an engine cleaning service, such as the cleaning service 18.The cleaning operations computing device 280 is communicatively coupledto the network(s) 260. The cleaning operations computing device 280includes an engine cleaning history database 292, and a cleaningparameters database 294. The engine cleaning database 292 storesinformation related to the cleaning history of the turbine engine system272, such as, for example, when was the last cleaning of the turbineengine 12 and what cleaning was performed. In an alternative embodimentof the invention, the engine cleaning history can also be stored on theengine maintenance history database 252. The cleaning parametersdatabase 294 includes information related to the cleaning regimensavailable to be used to clean a particular turbine engine 12, such asdata on all available cleaning regimens, which cleaning regimens areavailable at which locations, whether a cleaning crew at a particularlocation is available to perform a cleaning, and other informationrelated to the cleaning services 18. The cleaning operations computingdevice 280 may be embodied as any suitable computing device and/orelectrical circuitry for performing the functions described herein.Accordingly, remaining components of the cleaning operations computingdevice 280 having the same name as above-described components of theengine monitoring computing device 210 may be embodied similarly;therefore, the description is not repeated here.

In general, references herein to a “database” may refer to, among otherthings, a computerized data structure capable of storing information ina manner that enables the stored information to be later retrieved,e.g., by a query (e.g., a keyword search) or a computer program command.Portions of each database may be embodied as, for example, a file, atable, an extensible markup language (XML) data structure, or adatabase. While not specifically shown, the fleet management system 200may include other computing devices (e.g., servers, mobile computingdevices, etc.), which may be in communication with each other and/or theengine monitoring computing device 210 via one or more communicationnetworks 260, in order to perform one or more of the disclosedfunctions.

Additional features of the illustrative fleet wash management system 200include the following. The system 200 can obtain historical data aboutthe engine 12 or the engine's cleaning history, which the system 200 canuse to better utilize an engine cleaning scheme for the owner operator.Some embodiments of the system 200 can be used in conjunction with acomputing system of the engine manufacturer to schedule maintenanceintervals based upon certain parts or modules that need replacement. Aparticular example of this would be where the system 200 determines thatan engine merely needs a minor overhaul and thus initiates a cleaning.As a result, the engine is cleaned and returns to service, therebyextending the engine's efficiency until a major overhaul is required.The system 200 can issue a prompt or notification in order to preventthe occurrence of a scheduled cleaning cycle, if the system 200determines that the engine's removal from service is imminent (e.g., forregularly scheduled required maintenance). In other words, the system200 can coordinate cleaning cycles with other maintenance schedules aswell as operational schedules. The system 200 can algorithmicallyestablish the best variation of cycle times in which the optimumparameters of engine cleaning are determined, including the timeinterval between cleaning(s), the duration of cleaning(s), and theparticular mixture or composition of the cleaning solution. The system200 can monitor the engine autonomously, e.g., irrespective of whetheran engine cleaning is currently being performed. For example, the system200 can send a notification for a particular engine to e.g., theowner/operator, based on existing engine performance or maintenanceintervals. The system 200 can establish a predictive cleaning schedulebased on historical data. The predictive cleaning schedule can be usedby, e.g., the engine manufacturer, in order to better predict enginecleaning as a function of minor and major overhaul intervals.

Referring now to FIG. 3, an embodiment of the turbine engine system 272includes the turbine engine 12 and the engine controller 344. The enginecontroller 344 may be configured as, for example, a Full AuthorityDigital Engine Controller (FADEC), a component thereof, or as a separatemodule in communication with a FADEC (e.g., via one or more electroniccommunication links or networks). In some embodiments, the enginecontroller 344 includes an on-board engine health monitor 346, describedin more detail below.

The illustrative turbine engine 12 is a multi-shaft turbofan gas turbineengine; however, aspects of the present disclosure are applicable toother types of turbine engines, including various types of turboprop andturboshaft systems, as well as turbine engines designed fornon-aerospace applications. In the turbine engine 12, a fan 310 (e.g., afan, variable pitch propeller, etc.) draws air into the engine 12. Someof the air may bypass other engine components and thereby generatepropulsion thrust. The remaining air is forwarded to one or morecompressors 314. In some embodiments, a low pressure (LP) compressor mayincrease the pressure of air received from the fan 310, and a highpressure (HP) compressor may further increase the pressure of airreceived from the low pressure compressor. In any event, thecompressor(s) 314 increase the pressure of the air and forward thehigher-pressure air to a combustion section 316. In the combustionsection 316, the pressurized air is mixed with fuel, which is suppliedto the combustion section 316 by a fuel supply such as a fuel injector(not shown). Typically, a flow meter, flow control valve, or similardevice (e.g., a fuel flow sensor, FF 326) monitors and/or regulates theflow of fuel into the combustion section 316. An igniter (not shown) istypically used to cause the mixture of air and fuel to combust. Thehigh-energy combusted air is directed to one or more turbines 322, 324.In the illustrative embodiment, a high pressure turbine 322 is disposedin axial flow series with a low pressure turbine 324. The combusted airexpands through the turbines 322, 324, causing them to rotate. Thecombusted air is then exhausted through, e.g., a propulsion nozzle (notshown), which may generate additional propulsion thrust.

The rotation of the turbines 322, 324 causes engine shafts 312, 318, torotate. More specifically, rotation of the low pressure turbine 324drives the low pressure shaft 312, which drives the fan 310; whilerotation of the high pressure turbine 322 drives the high pressure shaft318, which drives the compressor(s) 314. In some embodiments, the shafts312, 318 may be concentrically disposed. In some embodiments, more thantwo shafts 312, 318 may be provided. For example, in some embodiments,an intermediate shaft is disposed concentrically between the lowpressure shaft 312 and the high pressure shaft 318 and supports anintermediate-pressure compressor and turbine.

The illustrative turbines 322, 324 additionally drive one or moreelectrical machines 332, e.g., via “more electric” technology and/orpower take-off assemblies 328, 330. The low pressure turbine 324 drivesa generator 334 via the low pressure shaft 312 and a power take-offassembly 328. The high pressure turbine 322 drives a motor/generator 336via the high pressure shaft 318 and a power take-off assembly 330. Theelectrical machines 332 can generate power, which may be supplied to anaircraft electrical system 338. For instance, the generator 334 maygenerate electrical power that is supplied to other components orsystems of the aircraft 270 or other vehicle to which it is coupled. Themotor/generator 336 may operate similarly, but may additionally have amotor mode in which it receives electrical energy from, for example, theaircraft electrical system 338, and converts the received electricalenergy into rotational power, which is then supplied to the highpressure turbine 322 via the power take-off assembly 330.

The illustrative engine controller 344 controls the overall operation ofthe engine 12. For example, the engine controller 344 controls the rateof fuel flow to the combustion section 316, as well as the airflowthrough the engine 12 (e.g., by varying the pitch angle of vanes of thefan 310). The engine controller 344 receives signals from a number ofdifferent sensors 326, which are installed at various locations on theengine 12 to sense various physical parameters such as temperature (T),shaft speed (SS), air pressure (P), and fuel flow (FF), which representvarious aspects of the current operating condition of the engine 12. Thesensors 326 transmit data signals representing the sensed information tothe engine controller 344. In response to the sensor signals, the enginecontroller 344 supplies various commands to the engine 12 to controlvarious aspects of the operation of the engine 12. Additionally, theengine controller 344 utilizes the sensor signal to perform enginehealth monitoring.

The engine health monitor 346 provides engine health monitoring andprognostics by monitoring the efficiency of the engine 12 as it relatesto engine performance, based on the sensor signals received from time totime by the engine controller 344. While shown in FIG. 3 as a sub-moduleof the engine controller 344, the engine health monitor 346 may beembodied as a stand-alone unit or as a sub-module of another computersystem. The engine health monitor 346 monitors the health of the engine12 by looking at fuel efficiency, engine speed, engine temperatureand/or other desired parameters, which are obtained or derived from thesensor signals transmitted by the sensors 326.

The illustrative engine health monitor 346 compares the real-time engineoperating conditions to an established “healthy engine” profile. Thehealthy engine profile may be developed over time using model-basedcontrol algorithms. Based on the comparison of the real-time operatingconditions to the healthy engine profile, the engine health monitor 346algorithmically generates engine health predictions. The engine healthpredictions may be different for each engine and for different operatingconditions, but the data for any engine can be gathered in a test celland then incorporated into the model-based engine health monitoringalgorithms. An illustrative example of an engine health monitorutilizing algorithms is established when the engine 12 is tested withina test cell for the purpose of proving that the engine 12 has achieveddesired certification and reliability requirement limits. This testinformation for specific engines is transferred to engine healthmonitoring units (such as the engine health monitor 346), and then,on-wing, the measured engine output is compared to or validated againsttest cell predictions. This will consent engine to engine modelvariability within engine repeatability. For instance, turbinetemperature measured in a test cell is compared with on-wing temperaturemeasurements following standard day and model corrections. If thevariation (e.g., the difference between the measurements obtained in thetest cell and the measurements obtained on-wing) exceeds installationeffects, then the system can conclude that the turbine temperature isdeteriorating over time. A trigger limit is set for each parameter orcombination of parameters that sets or is used to determine the need fora desired maintenance action. In the above example, low turbinetemperature margin results in nucleated foam wash at or within a certaintime period.

Referring now to FIG. 4, a simplified schematic diagram shows componentsof the computing system 200 in an operational environment 400 (e.g.,interacting at runtime). The components of the fleet management system200 shown in FIG. 4 may be embodied as computerized programs, routines,logic, data and/or instructions executed or processed by one or more ofthe computing devices 210, 240, 280, 344. Beginning at the top of FIG.4, the engine health monitor 346 of the turbine engine system 272obtains (e.g., via the sensors 326) and outputs engine health data 410to the engine performance monitor 230.

The engine performance monitor 230 may be embodied as a system that usesthe real-time feedback of engine health data 410 from the turbine enginesystem 272 to determine the health of the turbine engine 12 and/or oneor more other components of the turbine engine system 272. The enginehealth data 410 may include measurements of engine speed, enginetemperature, fuel efficiency, oil pressure, oil temperature, DC voltage,engine torque, engine pressure and/or other indicators of turbine engineperformance. The engine performance monitor 230 utilizes the enginehealth data 410 to generate one or more engine performance data 412(e.g., one or more parameters, such as an indicator of engineperformance, such as a data value or a plot of data values). Analternative embodiment of the engine performance monitor 230 includesreceiving engine performance parameters directly from the engine healthmonitor 346 of the turbine engine system 272. Alternatively or inaddition, the computing and tracking of engine health monitoring dataover time can be done by one or more external computing systems andtransmitted to the engine performance monitor 230 (e.g., by a network260).

The engine performance data 412 are output to the optimization routine238 of the cleaning schedule optimizer 232. The optimization routine 238determines whether a cleaning of the turbine engine 12 would improveperformance of the turbine engine system 272 enough to justifyinitiating a cleaning or establishing a cleaning schedule. Determinationof compressor fouling (e.g., whether cleaning is needed as a result ofthe compressor's condition) can be challenging. If there is any evidencethat a maintenance action is required for another cause, such as bleedleak, hot section deterioration or fluctuation in any one of theperformance parameters, then action should be taken by the system tominimize those other causes. In one method of optimization the systemranks or weights different criteria or parameters used in theoptimization routine. For example, if turbine temperature or core speedmargin is below a minimum limit, then a rank 1 is assigned in theoptimization routine, if margins are at certain range then a rank 2 isassigned, and detection of a combination of margins is assigned to rank3. Similarly, if time since last wash is achieved to maximum limit thenrank 1 is assigned. Based on the optimization routine rankassignment(s), the next available maintenance opportunity for theaircraft and ground equipment availability, the optimizer assesses theneed for a cleaning, generates a cleaning schedule, and notifies user,such as the cleaning crew and/or an airline operations or maintenanceteam, of the need for cleaning and/or the cleaning schedule. Theoptimization routine can provide not just one available cleaning optionbut can also list multiple possible cleaning opportunities.

In an alternative embodiment, the engine performance monitor 230 onlyoutputs engine performance data 412 to the optimization routine 238after a certain level of degradation of engine performance has beendetected. The illustrative cleaning schedule optimization routine 238receives other information from a number of different sources. Forexample, the optimization routine 238 utilizes engine usage data 414,which may be obtained from the engine usage database 250; enginemaintenance data 416, which may be obtained from the engine maintenancehistory database 252; engine cleaning history data 418, which may beobtained from an engine cleaning history database 292; and cleaningparameter data 420, which may be obtained from the cleaning parametersdatabase 294. The various source of data provide, for example,engine-specific information concerning the turbine engine system 272 andthe possible cleaning options.

The fuel efficiency calculator 234 of the cleaning schedule optimizer232 utilizes the engine performance data 412 to compute an estimate ofimproved fuel efficiency. The carbon credit calculator 236 of thecleaning schedule optimizer 232 utilizes the fuel efficiency data 422 tocompute carbon credit data 424 (e.g., an estimate of carbon credits thatcan be earned). The optimization routine 238 utilizes the computed data(e.g., carbon credit data and/or fuel efficiency data 422), as well hasengine health, engine performance, and other data mentioned above, todetermine the type of cleaning that is likely (e.g., statistically) tobe most effective, and computes the associated cleaning schedule for theturbine engine 12 (or more generally, for the aircraft 270) based on thereceived information or estimates, or a combination thereof.

For example, in some embodiments, based on the engine performance data412 received from the engine performance monitor 230, the cleaningschedule optimizer 232 queries a number of databases for informationregarding the turbine engine system 272 that is experiencing adegradation of engine performance. The cleaning schedule optimizer 232queries the engine usage database 250 for engine usage data 414. Theengine usage data 414 can include data regarding the types of flightsaircraft 270 has flown, the departure and destination locations of theaircraft 270, the date and time of flights of the aircraft 270, theclimate and weather data regarding where the aircraft 270 operated, andother contextual data that provides information about the operatingenvironment of the aircraft 270 and the associated turbine engine system272. The cleaning schedule optimizer 232 queries the engine maintenancehistory database 252 for engine maintenance data 416. The enginemaintenance data 416 can include a log of maintenance performed on theturbine engine system 272, including dates of the service, the dates ofscheduled maintenance, and possibly, the cleaning history of the turbineengine system 272. The cleaning schedule optimizer 232 queries theengine cleaning history database 292 to obtain engine cleaning history418. The engine cleaning history 418 includes information from thecleaning service 18 regarding past cleanings performed on the turbineengine 12, such as the cleaning regimens performed, the location atwhich the cleaning was performed, and when the cleaning was performed(e.g., date and time). The cleaning schedule optimizer 232 also queriesa cleaning parameters database 294 for cleaning parameter data 420.Cleaning parameter data 420 can include data about all of the availablecleaning regimens, the locations at which cleaning processes regimensare available, and the availability, or schedule, of the cleaning units10 that are available to perform the cleanings to clean an aircraft 270at a particular location.

The cleaning schedule optimizer 232 also takes the engine performancedata 412 and applies it to a fuel efficiency calculator 234. The fuelefficiency calculator 234 calculates the fuel efficiency of the turbineengine 12 based on the engine performance data 412. The fuel efficiencycalculator 234 also compares the current fuel efficiency data 422against past fuel efficiency data 422 of the turbine engine 12 toestimate an improvement in fuel efficiency due to the turbine engine 12having received a cleaning. The fuel efficiency calculator 234 can alsoconsider past improvements in fuel efficiency after the turbine engine12 received a cleaning and/or an estimate of the effectiveness of aparticular regimen when determining an estimate of improvement in fuelefficiency. The fuel efficiency data 422 that is output by the fuelefficiency calculator 234 can include the current fuel efficiency of theturbine engine 272 and the estimated improvement in fuel efficiency dueto a cleaning.

The carbon credit calculator 236 receives the fuel efficiency data 422and calculates an estimate for carbon credits earned, based on theestimate of the improvement in fuel efficiency of the turbine engine 272after a cleaning. Carbon credits are generally calculated by estimatinga specific fuel-consumption improvement and applying a carbon creditconversion. The exact amount of the carbon credit conversion is variablebased on the applicable laws regulating carbon emissions. Once anestimate of carbon credits earned is determined, the carbon creditcalculator 236 outputs carbon credit data 424 to the optimizationroutine 238.

The optimization routine 238 utilizes the data received by the cleaningschedule optimizer 232, including the engine performance data 412, theengine usage data 414, the engine maintenance data 416, the enginecleaning data 418, the cleaning parameter data 420, the fuel efficiencydata 422, and the carbon credit data 424. The optimization routine 238determines whether a cleaning would maximize cost savings for theowner/operator of the aircraft 270. For example, the optimizationroutine 238 would likely determine that a cleaning is necessary when theengine performance of the turbine engine system 272 has degraded past acertain point and the next scheduled overhaul of the engine is manyhours away. In contrast, if the engine performance has degraded, but thenext scheduled engine overhaul is scheduled to occur in a few hundredhours of flight time for the aircraft 270, the optimization routine 238would likely find that a cleaning is not necessary because the cleaningwould only be effective for a short period of time before the engineoverhaul was done. Another factor that the optimization routine 238would consider are what types of environments and weather the aircraft270 has been operating in. Certain types of cleaning regimens are morelikely to be effective against certain types of grime and dirt that areprevalent in certain environments.

In some embodiments, the optimization routine 238 is a function of lowturbine temperature margin (minimum limit), low core speed margin(minimum limit), time (and or cycle) since last wash (maximum limit),chosen fuel consumption reduction and environmental conditions such asmarine or high air quality index. In other words, the optimizationroutine performs mathematical computations (e.g., one or moreoptimization algorithms) using one or more of the foregoing pieces ofinformation as arguments or parameters. Once the optimization routine238 has determined that a cleaning is necessary or recommended, thecleaning schedule optimizer 232 outputs cleaning schedule data 426. Thecleaning schedule data 426 can include a simple notification that acleaning is due delivered to the cleaning service 18 and/or to theowner/operator of the aircraft 270, or may include a scheduling requestdirected to both the cleaning service and the owner/operator.Alternatively, the cleaning schedule optimizer 232 can directly initiateor schedule the cleaning and cause the aircraft 270 to receive acleaning at a particular location, likely between flights so as to notinterrupt the flight schedule of the aircraft 270. The cleaning scheduledata 426 is output from engine monitoring computing device 210 throughcommunication subsystem 228 and received by communication subsystem 256of the fleet operations computing device 240 and received bycommunication subsystem 296 of the cleaning operations computing device280. In some embodiments, after receiving cleaning schedule data 426,communication subsystems 256 and 296 communicate directly with eachother to finalize the scheduling for the cleaning of the turbine engine12.

Referring now to FIG. 5, an illustrative method 500 for analyzingwhether a cleaning would maximize engine performance, while minimizingoperating costs of the engine, is shown. Aspects of the method 500 maybe embodied as computerized programs, routines, logic and/orinstructions executed by the fleet management system 200, for example byone or more of the modules 230, 232, 234, 236, 238, 250, 252, 292, and294. At block 510, the system 200 obtains engine health monitoring data510 from the turbine engine system 272. The engine health monitoringdata may include measurements of engine speed, engine temperature, fuelefficiency, oil pressure, oil temperature, DC voltage, engine torque,engine pressure and other indicators of engine performance. The system200 may obtain the engine health monitoring data by, for example,receiving user-generated or system-generated input via the userinterface subsystem 226 and/or the communication subsystem 228. At block512, the system 200 calculates engine performance parameters based onthe engine health data received. The engine performance parametersprovide information about the engine's performance over time includingthe temperature, engine speed, fuel consumption, and other parameters.At block 514, the system 200 analyzes the engine performance parametersto determine if the engine has experienced a significant drop in engineperformance. Engine performance may degrade when, for example, theoperating temperature of the engine increases, the speed of the enginedecreases, or the fuel consumption of the engine increases. These typesof patterns can show that the turbine engine is experiencing greaterresistive forces, which could include dirt and grime build up in theturbine engine. If no significant engine performance has occurred then,at block 536, the information is stored in the machine learning database222 for future use in machine learning applications, and the system 200continues to check engine performance parameters, either continuously orperiodically, until the performance of the engine degrades.

If at block 514, the system 200 determines that the engine performancehas degraded significantly then the engine performance parameters arepassed to the cleaning schedule optimizer 232 to optimize a cleaningschedule. As part of the optimization process, at block 516, 518, 520,and 522, the system 200 obtains information, generally stored on otherdatabases, for use in its optimization algorithm. The fleet managementsystem 200 may obtain the relevant by, for example, receivinguser-generated or system-generated input via the user interfacesubsystem 226 and/or the communication subsystem 228. At block 516, thesystem 200 obtains the maintenance history of the engine. At block 518,the system 200 obtains the engine usage data. At block 520, the system200 obtains the cleaning history of the engine. At block 522, the system200 obtains the maintenance parameters of the cleaning regimen. Thesetypes of data, and their relevant sources, have been described above andmay be embodied similarly, therefore, the description is not repeatedhere.

At block 524, the system 200 calculates the fuel efficiency parametersof the engine, including tracking past fuel efficiency measures,tracking the current fuel efficiency of the engine, and providing asimple estimate of a future improvement in fuel efficiency. The fuelefficiency parameters are used, at block 526, to calculate an estimateof carbon credits earned based on the estimated improvement in specificfuel consumption.

At block 528, the optimization routine 238 is executed. The optimizationroutine 238 considers all of the data received by the cleaning scheduleoptimizer 232 and algorithmically determines whether a cleaning shouldoccur, at block 530. The optimization routine 238 considers the pastmaintenance history of the engine 12, where the engine has beenoperating, past cleanings of the engine 12, and what future maintenanceis scheduled. The optimization routine 238 also considers the likelyeffectiveness of the cleaning regimens available. These considerationsgenerally include analyzing where the engine has been operating,determining what types of dirt and grime are in the engine compartment,also considering what types of flights and use the engine has beenreceiving. If the degradation of the engine performance can be explainedby dirt build-up in the engine and the engine compartment, theoptimization routine 238 is likely to suggest a cleaning. Other factorsthat the optimization routine 238 may consider include the estimatedcost of the cleaning, both the direct cost of the cleaning and anyindirect costs that can result from taking an aircraft out of servicetemporarily. Cost savings are also considered, including carbon creditsearned and the reduced costs that are associated with increased fuelefficiency. If the optimization routine 238 determines that no cleaningshould take place then the data gathered is stored in the machinelearning database 222 to help the fleet management system 200 use morepredictive models when determining whether a cleaning is necessary.

If a cleaning is necessary, at block 532, the fleet management system200 initiates a cleaning, e.g., by sending out schedule notifications.The system 200 may send the scheduling notifications by, for example,transmitting a user-generated or system-generated output via thecommunication subsystem 228. The types of scheduling notifications cantake a number of different forms including a gentle reminder sent to theinterested parties that cleaning for a particular turbine engine issuggested, sending out an invitation to accept a specific date and timefor a cleaning, or scheduling a cleaning automatically. The interestedparties are, generally, the owner/operator of the turbine engine 12 andthe cleaning service 18 responsible for cleaning the engine. At block534, the cleaning is performed, e.g., in response to receiving acleaning notification. Following block 534; the method 500 may concludeor proceed to block 536.

At block 536, the data for the cleaning of the engine is store in themachine learning database 222 for future use. Machine learning involvesthe execution of mathematical algorithms on samples of data collectedover time, in order to discern patterns in the data that can be used topredict the likelihood of occurrence of future instances of the samedata. In the predictive process of determining an optimum time toprovide a cleaning to a turbine engine, machine learning algorithms canbe used to improve the optimization algorithms. The data from thedifferent stages of the optimization process is stored, as well as thefinal outcomes, so that future uses of the optimization algorithm can beadjusted to better meet the needs of those using the cleaning managementsystem. After the data has been stored in the machine learning database222, or following block 534 in some embodiments, the system 200 returnsto block 510.

In the drawings, specific arrangements or orderings of schematicelements may be shown for ease of description. However, the specificordering or arrangement of such elements is not meant to imply that aparticular order or sequence of processing, or separation of processes,is required in all embodiments. In general, schematic elements used torepresent instruction blocks or modules may be implemented using anysuitable form of machine-readable instruction, and each such instructionmay be implemented using any suitable programming language, library,application programming interface (API), and/or other softwaredevelopment tools or frameworks. Similarly, schematic elements used torepresent data or information may be implemented using any suitableelectronic arrangement or data structure. Further, some connections,relationships or associations between elements may be simplified or notshown in the drawings so as not to obscure the disclosure.

This disclosure is to be considered as exemplary and not restrictive incharacter, and all changes and modifications that come within the spiritof the disclosure are desired to be protected.

1. A method for optimizing cleaning of a turbine engine that is executedby one or more computing devices, the method comprising: receiving, by acommunication link between a turbine engine and a cleaning scheduleoptimizer, engine health data from the turbine engine over time duringoperation of the turbine engine; periodically executing, by the cleaningschedule optimizer, a cleaning optimization routine to evaluateinstances of the engine health data using one or more cleaning scheduleoptimization criteria; and in response to one or more instances of theengine health data meeting an engine health criterion, causing a foamedcleaning agent to be discharged into the turbine engine according to anoptimized engine cleaning schedule.
 2. The method of claim 1, whereinperiodically executing the cleaning optimization routine comprisesexecuting the cleaning optimization routine in response to determiningthat engine performance is degrading.
 3. The method of claim 1, furthercomprising querying, by the cleaning schedule optimizer, an operationaldatabase to obtain information about the use of the turbine engine andincorporating the turbine engine use information into the optimizationroutine.
 4. The method of claim 1, further comprising querying, by thecleaning schedule optimizer, an environmental database for informationabout operating environments of the turbine engine and incorporating theoperating environment information into the optimization routine.
 5. Themethod of claim 1, further comprising querying, by the cleaning scheduleoptimizer, a maintenance database for information about the maintenancehistory of the turbine engine and incorporating the maintenance historyinformation into the optimization routine.
 6. The method of claim 1,further comprising querying, by the cleaning schedule optimizer, acleaning parameters database for information about the differentcleaning regimens available for use on the turbine engine andincorporating the cleaning regimen information into the optimizationroutine.
 7. The method of claim 1, further comprising receiving, by afuel efficiency calculator electrically connected to an engine healthmonitor, one or more engine performance parameters and generating fuelefficiency parameters based upon the received engine performanceparameters.
 8. The method of claim 7, further comprising calculating, bythe fuel efficiency calculator, changes in fuel consumption in theengine over time.
 9. The method of claim 8, further comprisingcalculating, by the fuel efficiency calculator, changes in operatingcost over time based on the changes in fuel consumption over time. 10.The method of claim 7, further comprising receiving, by a carbon creditcalculator, the fuel efficiency parameters and the engine performanceparameters, estimating a change in fuel consumption based upon theoptimized cleaning schedule, and using the estimated change in fuelconsumption to calculate an estimated number of carbon credits earned.11. The method of claim 10, further comprising sending, by anotification system in communication with the cleaning scheduleoptimizer and coupled to a network, a notification to an owner of theturbine engine, and wherein the notification comprises the cleaningschedule, the estimated fuel consumption, and the estimated carboncredits.
 12. An engine cleaning optimizer embodied in one or moremachine accessible storage media and comprising instructions executableby a computing system comprising one or more computing devices to causethe computing system to: periodically receive instances of engine healthmonitoring data produced by a turbine engine during operation of theturbine engine; with the instances of engine health monitoring data,calculate an engine health parameter; with the engine health parameter:compute an indicator of engine performance degradation; compute anindicator of fuel consumption; and with the fuel consumption indicator,estimate a carbon credit that would result from cleaning the turbineengine; with the engine performance indicator, the fuel consumptionindicator, and the estimated carbon credit, generate an optimizedcleaning schedule; and initiate discharge of a foamed cleaning agentinto the turbine engine in accordance with the optimized engine cleaningschedule.
 13. The engine cleaning optimizer of claim 12, comprisinginstructions executable to generate the cleaning schedule for theturbine engine system by algorithmically evaluating the indicator ofengine performance degradation.
 14. The engine cleaning optimizer ofclaim 13, comprising instructions executable to generate the cleaningschedule for the turbine engine system by algorithmically evaluating acost of cleaning.
 15. The engine cleaning optimizer of claim 14,comprising instructions executable to generate the cleaning schedule forthe turbine engine system by algorithmically evaluating an estimatedfuel savings.
 16. The engine cleaning optimizer of claim 15, comprisinginstructions executable to generate the cleaning schedule for theturbine engine system by algorithmically evaluating an amount of timeuntil the next schedule maintenance for the engine.
 17. The enginecleaning optimizer of claim 16, comprising instructions executable togenerate the cleaning schedule for the turbine engine system byalgorithmically evaluating a likely effectiveness of the cleaning. 18.The engine cleaning optimizer of claim 17, comprising instructionsexecutable to generate the cleaning schedule for the turbine enginesystem by algorithmically evaluating an estimate of carbon creditsearned.
 19. The engine cleaning optimizer of any of claims 12,comprising instructions executable to modify the optimized cleaningschedule in response to data indicative of a maintenance schedule forthe turbine engine.
 20. The engine cleaning optimizer of any of claims12, comprising instructions executable to communicate with a computingsystem of the engine manufacturer to schedule maintenance intervalsbased on data indicative of parts or modules that need replacement.